feat(remote-feature-flag-controller): segment threshold flags by metaMetricsFlags with canonical ID default - #9325

Summary

• Add required getCanonicalProfileId constructor callback and metaMetricsFlags map for threshold flag segmentation.
• Threshold flags use canonical profile ID by default; flags whose names are present in metaMetricsFlags use MetaMetrics ID instead.
• Generalize threshold calculation to hash the selected segmentation ID while preserving the existing deterministic bucketing behavior.
• Pass the new segmentation options through @metamask/wallet remote feature flag controller initialization.

Segmentation Behavior

If the selected identifier is empty, threshold arrays are preserved as-is and not processed.

Example threshold config using canonical segmentation by default:

{
  "myCanonicalFlag": [
    {
      "name": "groupA",
      "scope": { "type": "threshold", "value": 0.5 },
      "value": "valueA"
    },
    {
      "name": "groupB",
      "scope": { "type": "threshold", "value": 1.0 },
      "value": "valueB"
    }
  ]
}

Example controller setup for a flag that should keep MetaMetrics segmentation:

new RemoteFeatureFlagController({
  // ...
  getMetaMetricsId,
  getCanonicalProfileId,
  metaMetricsFlags: {
    legacyMetaMetricsFlag: true,
  },
});

Migration

Consumers must pass getCanonicalProfileId for threshold flags that should use canonical profile segmentation, which is now the default for flags absent from metaMetricsFlags.

Existing threshold flags that must keep MetaMetrics-based bucketing should be listed in metaMetricsFlags and continue to provide getMetaMetricsId.

Test plan

• yarn workspace @metamask/remote-feature-flag-controller run jest --no-coverage src/utils/user-segmentation-utils.test.ts src/remote-feature-flag-controller.test.ts
• Threshold flags absent from metaMetricsFlags use getCanonicalProfileId for segmentation
• Threshold flags present in metaMetricsFlags use getMetaMetricsId for segmentation
• Threshold arrays are preserved when the selected identifier is empty
• Threshold cache entries use the selected segmentation ID and stale entries are cleaned up when flags are removed from the server response

Related

• Documentation: MetaMask/contributor-docs#176
• Ticket - https://consensyssoftware.atlassian.net/browse/MCWP-662